Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

I signed it!

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

Yea, it was me and I approve with this commit

It's me, I'm the same person, I approve with the commits

Last comment:

In the Can change current working directory to 'test-project' test could you use this option instead of what we're currently doing (which is the same thing but manually).

Can you rebase? I'll merge this when it's ready (or rebase myself later today).

I was away, sorry.
It's done, Rebased, ready for merge. Cheers!

Looks like the npm link is done after the npm install which defeats the purpose as it does not reduce install time nor size of node_modules. @filipesilva @monojack @monodnb Please review.

As a workaround, i use:

ng new --link-cli --skip-npm myproject
cd myproject
npm install

Woud love to have it in one command. Thanks.

With from @aecz 's process, link-cli is a large improvement in project setup time. Might it be worthwhile to make that process the default you get with "ng new"? In other words, make the fast path default, and the slow (but more correct, from a version-locking point of view) optional? It seems this really improves the CLI user experience. (Currently running ng-new is pretty fast on my Macbook, not so fast on most of Windows machines.)

Made a new pull request to address this
#2250

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}